Systems and Methods for Service in Multimedia Broadcast Multicast Services

ABSTRACT

A method for providing service among a plurality of Multicast Broadcast Single Frequency Networks (MBSFNs) that are providing multimedia broadcast services, includes storing a pointer in data to be transmitted by a base station corresponding to a serving of a first MBSFN. The pointer points to either a location of a multimedia broadcast multicast service (MBMS) control channel or a location of MBMS data in a second MBSFN.

RELATED APPLICATIONS

This application is based upon and claims the benefit of priority fromU.S. Provisional Patent Application No. 61/515,337, filed Aug. 5, 2011,the entire contents of which are incorporated herein by reference.

FIELD OF THE DISCLOSURE

This disclosure relates to systems and methods for service in multimediabroadcast multicast services in a wireless communication system.

BACKGROUND

A multicast and/or broadcast service (MBS), also known as a multimediabroadcast multicast service (MBMS), provides content data to a pluralityof users who desire to receive such a service in a communicationnetwork. For example, the content data may include movies, games, files,software programs, or TV programs, and may be provided by one or morecontent providers.

Conventionally, a plurality of Multicast Broadcast Single FrequencyNetworks (MBSFNs) may each provide the MBMS. For example, two separateMBSFNs may provide the same MBMS (broadcasting service). Accordingly,base stations within a MBSFN provide data with respect to the MBMS to auser equipment (UE). Each base station corresponds to a cell, the areato which a base station provides signals. Therefore, all the cellsincluded in a MBSFN may provide the MBMS data. Conventionally, when auser moves from one MBSFN to another, the conventional transmissionschemes might result in service continuity problems. For example, if auser moves across the boundary of one MBSFN to a new MBSFN, UE needs todisconnect from a cell in the current MBSFN and hand off to a cell inthe new MBSFN. The handoff process requires the UE to stop receiving theMBMS data in a current cell, connect to another cell in the new MBSFN,search for the service information of the MBMS in the cell of the newMBSFN, and start to receive the MBMS again.

SUMMARY

According to one of the embodiments of the present disclosure, there isprovided a method of providing service among a plurality of MBSFNs,wherein each MBSFN contains one or more cells, while a UE of a wirelesscommunication system receives a broadcasting service in a serving cellof the one or more cells in one of the MBSFNs. The method comprisesstoring a pointer in data to be transmitted by a base stationcorresponding to the serving cell in a first one of the MBSFNs, thepointer stored in a MBMS control channel (MCCH) of the first MBSFN andpointing to either a location of MCCH or MBMS data in a second one ofthe MBSFNs, or the pointer stored in a system information block of thefirst MBSFN and pointing to the location of the MCCH in the secondMBSFN; and transmitting the data by the base station for the first MBSFNfor receipt by the UE.

According to one of the embodiments of the present disclosure, there isprovided a method of providing service among a plurality of MBSFNs for aUE of a wireless communication system. The method comprises receivingdata by the UE from a base station that is included in a first one ofthe MBSFNs; determining by the UE whether the received data includes apointer to a second one of the MBSFNs, the pointer stored in a MCCH ofthe first one of the MBSFNs and pointing to either a location of MCCH orMBMS data in the second one of the MBSFNs or the pointer stored in asystem information block of the first one of the MBSFNs and pointing tothe location of the MCCH in the second one of the MBSFNs; and sending bythe UE a service join request to the second one of the MBSFNs forcontinuing the MBMS being received from the first one of the MBSFNsbased on the pointer.

According to one of the embodiments of the present disclosure, there isprovided a UE to receive an MBMS, comprising one or more processors, theone or more processors being configured to: receive data from a basestation that is included in a first one of MBSFNs; determine whether thereceived data includes a pointer to a second one of the MBSFNs, thepointer stored in an MCCH of the first one of the MBSFNs and pointing toeither a location of MCCH or MBMS data in the second one of the MBSFNsor the pointer stored in a system information block of the first one ofthe MBSFNs and pointing to the location of the MCCH in the second one ofthe MBSFNs; and send a service join request to the second one of theMBSFNs for continuing the MBMS being received from the first one of theMBSFNs based on the pointer.

According to one of the embodiments of the present disclosure, there isprovided a non-transitory computer-readable storage medium storing oneor more programs, wherein the one or more programs comprise instructionsthat, when executed by a computing device, cause the device to: receivedata from a base station that is included in a first one of MulticastBroadcast Single Frequency Networks (MBSFNs); determine whether thereceived data includes a pointer to a second one of the MBSFNs, thepointer stored in a multimedia broadcast multicast service (MBMS)control channel (MCCH) of the first one of the MBSFNs and pointing toeither a location of MCCH or MBMS data in the second one of the MBSFNsor the pointer stored in a system information block of the first one ofthe MBSFNs and pointing to the location of the MCCH in the second one ofthe MBSFNs; and send a service join request to the second one of theMBSFNs for continuing a MBMS being received from the first one of theMBSFNs based on the pointer.

It is to be understood that both the foregoing general description andthe following detailed description are exemplary and explanatory only,and are not restrictive of the invention, as claimed.

BRIEF DESCRIPTION OF THE DRAWINGS

The accompanying drawings, which are incorporated in and constitute apart of this specification, illustrate embodiments of the invention and,together with the description, serve to explain the principles of theinvention.

FIG. 1 illustrates a block diagram of a system for providing servicebetween a plurality of MBSFNs, according to an exemplary embodiment.

FIG. 2 illustrates a block diagram of another system for providingservice between a plurality of MBSFNs, according to an exemplaryembodiment.

FIG. 3 illustrates a method for providing service between a plurality ofMBSFNs, according to an exemplary embodiment.

FIG. 4 illustrates a method for providing service in MBSFNs for a UE ofa wireless communication system, according to an exemplary embodiment.

FIG. 5 illustrates pointer relationships, according to an exemplaryembodiment.

FIG. 6 illustrates a determination of edge cells based on cellidentities, according to an exemplary embodiment.

FIG. 7 illustrates another pointer for carrier services, according to anexemplary embodiment.

FIG. 8 illustrates a determination of edge cells for various carrierservices within an MBSFN, according to an exemplary embodiment.

FIG. 9 illustrates a block diagram of a base station, according to anexemplary embodiment.

FIG. 10 illustrates a block diagram of a UE, according to an exemplaryembodiment.

DESCRIPTION OF THE EMBODIMENTS

Reference will now be made in detail to exemplary embodiments, examplesof which are illustrated in the accompanying drawings. The followingdescription refers to the accompanying drawings in which the samenumbers in different drawings represent the same or similar elements,unless otherwise represented. The implementations set forth in thefollowing description of exemplary embodiments consistent with thepresent invention do not represent all implementations consistent withthe invention. Instead, they are merely examples of systems and methodsconsistent with aspects related to the invention, as recited in theappended claims.

In exemplary embodiments, there are provided systems and methods withrespect to data transmission for multicast broadcast services (MBSs),also known as multimedia broadcast multicast services (MBMSs), over aplurality of single frequency networks. The application of a singlefrequency network in an MBMS is referred to as a Multicast BroadcastSingle Frequency Network (MBSFN) in 3 G communication systems. Aplurality of MBSFNs, according to some embodiments, may provide the sameMBMS (broadcasting service). Each MBSFN may include one or more cells. Acell refers to an area of service covered by a respective base station.In some embodiments, a user equipment (UE) receiving a broadcastingservice or MBMS that is provided over two separate MBSFNs may travelfrom the coverage area of a first MBSFN to a second MBSFN. The cellproviding the broadcasting service or MBMS to the UE at a particulartime may be referred to as a serving cell. According to exemplaryembodiments, in a handoff process, a UE may stop receiving an MBMS fromthe current serving cell in the first MBSFN and connect to anotherserving cell in the second MBSFN. Exemplary embodiments may utilizepointers provided in data from the current serving cell in the firstMBSFN to make the handoff process possibly more efficient. Pointers maybe included in the signals of an MBMS transmission in the first MBSFNand provide the UE with the information of nearby cells that are part ofthe second MBSFN. The UE can then utilize information in the pointer tolocate the MBMS data in the second MBSFN, as soon as it comes within thecoverage area of a cell (serving cell) in the second MBSFN. Accordingly,when the UE moves from the first MBSFN to the second MBSFN, the UEutilizing the pointer does not need to disconnect from the MBMS andsearch for a system information block (SIB) from the new cell, whichwould entail disconnecting and reconnecting to the MBMS. Instead, the UEmay start receiving the MBMS in the second MBSFN once it enters the cellcoverage because the UE already has been provided information throughthe pointer on where to seek the MBMS data when the UE enters the secondMBSFN's coverage area. Accordingly, a pointer providing informationrelated to the MBMS data location and MBSFN area information mightenables the UE to avoid disruption of service continuity.

Accordingly, in some embodiments, a system information block (SIB) maybe generated on a cell basis to be broadcast by a corresponding basestation to a UE. As a result, the UE can receive the SIB once it entersthe coverage area of a particular cell. The SIB included a service areaidentity (SAI) of an MBMS and the frequency of the MBMS, as MBMSassistance information. Since the SIB is a cell-specific message,different cells broadcast SIBs have different contents. For each cell,the UE, after receiving the SIB, locates the frequency of MBMS data inan MBMS control channel (MCCH). The information in the MCCH may indicatethat channels that comprise multicast channel (MCH) data are identicalthroughout an MBSFN. The MCCH carries the frequency and offset of theMCH. That is, the UE may receive the MBMS, which is in the MCH, after itreads the MCCH.

Accordingly, in some exemplary embodiments, a pointer may be stored inthe data that comprises an SIB or an MCCH that is being transmitted in acell in a first MBSFN. For example, the pointer may be stored in theMCCH of the first MBSFN and point to either a location of the MCCH orMBMS data in a second MBSFN. Alternatively, the pointer may be stored inthe SIB of the first MBSFN and point to the location of the MCCH in thesecond MBSFN. This data including the pointer may then be transmitted toa UE from a base station in the cell.

As the UE begins to transition from the first MBSFN to the second MBSFN,the handoff process might be more efficient, as the UE does not need toreceive the SIB from a cell of the second MBSFN; instead, the UE alreadyknows the location of either the MCCH or the MCH in the next servingcell from the second MBSFN. Accordingly, the UE might be able to startreceiving the MBMS or the broadcasting service with less delay orwithout delay.

FIG. 1 illustrates a block diagram of a system 100 for providing servicebetween a plurality of MBSFNs, according to an exemplary embodiment.System 100 includes an MBSFN 102 and an MBSFN 104. System 100 includesone or more base stations, such as base stations 106, 108, 110, and 112.For example, base stations 106 and 108 may be in MBSFN 102, and basestations 110 and 112 may be in MBSFN 104. The area covered by signalsfrom a base station is referred to as a cell. For example, cell 116corresponds to base station 106, cell 118 corresponds to base station108, cell 120 corresponds to base station 110, and cell 122 correspondsto base station 112. In addition, system 100 further includes at leastone UE 114 that receives an MBMS or broadcasting service from basestations 106, 108, 110, and 112 when it is within the cell of eachrespective base station. In an exemplary embodiment, UE 114 travels on apath 124 from cell 116 to cell 122. MBSFN 102 and MBSFN 104 are adjacentto each other and contain cells 108 and cells 110, respectively, thatare adjacent to each other.

Utilizing methods discussed below according to exemplary embodiments,users might be able to efficiently access and receive broadcastingservice data or MBMS data as UE 114 transitions from the coverage areaof MBSFN 102 to the coverage area of MBSFN 104.

FIG. 2 illustrates a block diagram of a system 200 for providing servicebetween a plurality of MBSFNs, according to an exemplary embodiment.System 200 includes an MBSFN 202 and an MBSFN 204. System 200 includesone or more base stations, such as base station 206. Cell 208corresponds to base station 206. Additionally, base station 206 isincluded in both MBSFN 202 and MBSFN 204. Accordingly, MBSFN 202 andMBSFN 204 overlap over cell 208. Therefore, cell 208 is a serving cellfor a UE 210 that receives broadcasting services from base station 206in both MBSFNs 202 and 204. In an exemplary embodiment, UE 210 travelson a path 212 from MBSFN 202 to MBSFN 204. While only base station 206is illustrated in FIG. 2, MBSFNs 202 and 204 may contain additional basestations with corresponding cells.

Utilizing methods discussed below according to exemplary embodiments,users might be able to efficiently access and receive broadcasting dataor MBMS data as UE 210 transitions from MBSFN 202 and MBSFN 204. Forexample, cell 208 may serve as an edge cell of MBSFN 202 and MBSFN 204.Therefore, cell 208 may provide information corresponding to MBSFN 204in the data transmitted for MBSFN 202 to the UE 210. Then based on theinformation corresponding to MBSFN 204, UE 210 may acquire MBMS datafrom MBSFN 204 in cell 208.

FIG. 3 illustrates a method 300 for providing service between aplurality of MBSFNs, according to an exemplary embodiment.

First, a pointer is stored in data to be transmitted by a respectivebase station corresponding to a serving cell among one or more cells ina first one of the MBSFNs (step 302). The pointer stored in the data maybe a stored MCCH of the first MBSFN and may point to either a locationof the MCCH or MBMS data in a second one of the MBSFNs, or the pointermay be stored in an SIB of the first MBSFN and point to the location ofthe MCCH in the second MBSFN. For example, referring back to FIG. 1, thepointer may be stored in data to be transmitted by base station 108,which is adjacent to base station 110.

FIG. 5 illustrates pointer relationships according to an exemplaryembodiment. For example, a first MBSFN 502 and a second MBSFN 504 areshown. A UE (not shown in FIG. 5) is assumed to be currently provided anMBMS by a serving cell in MBSFN 502. Therefore, MBSFN 502 is consideredthe current serving MBSFN, and MBSFN 504, to which the UE hands off, isconsidered the target MBSFN. MBSFNs 502 and 504 may be similar to MBSFNs102 and 104 (shown in FIG. 1), respectively, as well as MBSFNs 202 and204 (shown in FIG. 2), respectively. SIB 506, MCCH 508, and MCH 510 maybe contained within information being provided to the UE by the servingcell in MBSFN 502. Similarly, SIB 512, MCCH 514, and MCH 516 may becontained within information being provided by a cell in MBSFN 504. Forexample, assuming MBSFNs 502 and 504 are similar to MBSFNs 102 and 104,respectively, shown in FIG. 1, SIB 506, MCCH 508, and MCH 510 may betransmitted by base station 108, and SIB 512, MCCH 514, and MCH 516 maybe transmitted by base station 110. Furthermore, a pointer 520 in SIB506 points to the location of MCCH 514 in MBSFN 504. Pointers 522 and524 in MCCH 508 point to MCCH 514 and MCH 516, respectively.Accordingly, before the UE connects to MBSFN 504, the UE is aware of thelocation of either MCCH 514 or MCH 516 of MBSFN 504. Pointers 520, 522,and 524 are all illustrated as being stored in MBSFN 502. However, anyof pointers 520, 522, and 524 may be stored independently or as acombination. For example, data that is stored to be broadcast by basestation 108 in cell 118 may only include pointer 520 in SIB 506generated for cell 118. Therefore, UE 114 may access MBMS data based onpointer 520 indicating the location of MCCH 514 in MBSFN 504.

Next, referring back to the method shown in FIG. 3, the data istransmitted from the base station of the first MBSFN (step 304). Forexample, base station 108 may transmit the data in cell 118 for MBSFN102. Accordingly, UE 114, when located within the coverage area of cell118, may receive this data including pointers with respect to cell 120of MBSFN 104.

FIG. 4 illustrates a method 400 for providing service in MBSFNs for a UEof a wireless communication system, according to an exemplaryembodiment.

First, data is received at the UE from a base station that is includedin a first MBSFN (step 402). For example, UE 114 receives data in cell118 based on signals from base station 108 while traveling on path 124.

Next, it is determined whether the received data includes a pointer to asecond MBSFN (step 404). A pointer may be stored in the data in thefirst MBSFN and point to either a location of the MCCH or MBMS data inthe second MBSFN, or the pointer may be stored in an SIB of the firstMBSFN and point to the location of the MCCH in the second MBSFN. Forexample, the data received by UE 114 in cell 118 of MBSFN 102 mayinclude information related to cell 120 in MBSFN 104. For example,pointer 520 may be included in SIB 506 that points to the location ofMCCH 514 in MBSFN 504. Accordingly, when a handoff occurs for UE 114while travelling on path 124 from cell 118 to cell 120, instead of firstacquiring SIB in a cell of MBSFN 104, UE 114 may already know where MCCHis located in the cell of MBSFN 504. For example, instead of firstacquiring SIB 512 of MBSFN 504, UE 114 may already know where MCCH 514is located.

Next, a service join request is sent to the second MBSFN for continuinga broadcasting service being received from the first MBSFN based on thepointer (step 406). For example, if information is provided to UE 114 bySIB 506 regarding the location of MCCH 514 in MBSFN 104, as soon as thehandoff occurs, UE 114 is able to request continuing the broadcastingservice (MBMS) based on a pointer from cell 120. That is, SIB 512 doesnot have to be acquired by UE 114 to locate MCCH 514. Accordingly,pointer 520 allows UE 114 to know the location of MCCH 514 as soon asthe handoff occurs and to access the MBMS in MCH 516.

In an exemplary embodiment, it may be determined before step 404 thatthe serving cell is an edge cell of the first MBSFN, which may determineif the received data includes a pointer. Accordingly, the determinationto check whether a pointer is included or not would only take place whenit is determined that the serving cell is an edge cell, for possiblymore efficient use of resources by UE 114.

In some embodiments, if the serving cell is not an edge cell of thefirst MBSFN, the UE does not process the step of determining whether thereceived data includes the pointer.

In some embodiments, if the serving cell is not an edge cell of thefirst MBSFN, the UE does not process the step of sending a service joinrequest to the second one of the MBSFNs.

In some embodiments, the serving cell may be determined to be an edgecell by inspecting a list of edge cells accessible to UE 114.Alternatively, a determination may be made that the serving cell is anedge cell as a function of a calculation based on a least commonmultiple (LCM) of the edge cell identities.

FIG. 6 illustrates a determination of edge cells based on cellidentities, according to an exemplary embodiment. An exemplary MBSFN 602includes cells having cell identities 3, 5, 6, 7, 8, 9, 11, 12, and 15.Every cell apart from cell 7 may be an edge cell. Therefore, the valuesof the edge cells 3, 5, 6, 8, 9, 11, 12, and 15 may be utilized toproduce a function based on cell identities. For example, the LCM ofcell identities for cells 3, 5, 6, 8, 9, 11, 12, and 15 is 1320.Accordingly, a function can be included that the LCM is divided by aserving cell's identity number to determine if it is an edge cell. Forexample, 1320 divided by 15—the identity of cell 15—produces a wholenumber, which indicates that cell 15 is an edge cell. However, 1320divided by 7—the identity of cell 7—produces a fraction, indicating thatit is not an edge cell. This function may be carried out in UE 114(FIG. 1) to determine whether it is currently operating in an edge cellor not. Accordingly, when the serving cell is an edge cell, the UE cancheck whether pointers are included in the data provided to it. However,if the serving cell is not an edge cell, a handoff to a different MBSFNis not likely to occur; therefore, there is no need to check forpointers.

In other exemplary embodiments, cyclic redundancy checks or otherencoding techniques may be applied to detect whether a serving cell isan edge cell.

In some exemplary embodiments, multiple carrier services may be providedwithin a cell that is covered by a base station. An MBMS may utilize oneor more of these multiple carrier services. Accordingly, all of thecarrier services to which a UE may potentially connect may not providethe MBMS. In such a case, a second inter-cell pointer can be includedthat points to carrier services providing MBMS in a particular cell.

FIG. 7 illustrates examples of such a second pointer for carrierservices, according to an exemplary embodiment. With reference to FIG.7, multiple service carriers 702, 704, 706, and 708 are available incell 710. It is possible that an MBMS or a broadcasting service may bespecified to be carried by only some of the multiple service carriers,for example, carriers 702, 706, and 708, that may be available in cell710. However, the MBMS data or the broadcasting service data mayactually be transmitted only over carriers 702 and 708. Accordingly,pointers may indicate that carrier services 702 and 708 are the only twocarrier services that provide data. Therefore, pointers indicatingcarrier services specify the location of carrier services within cell710.

Therefore, in the exemplary embodiment shown in FIG. 7, pointers pointto carrier services 702 and 708, through which the broadcasting servicecontents may be actually distributed. A pointer 712 in carrier service702 specifies the position of carrier service 708, and indicates to auser that carrier service 708 contains the actual broadcasting service.This prevents a user from switching to carrier service 706. Althoughcarrier service 706 is specified as carrying the broadcasting service,it does not actually contain contents of the MBMS data or thebroadcasting service data. Similarly, a pointer 714 from carrier service708 points to carrier service 702.

Pointers 716 from carrier service 706 point to carrier services 702 and708, as they both may contain actual contents of the broadcastingservice. Accordingly, if UE 114 attempts to connect to carrier service706 to receive broadcasting services, UE 114 can quickly switch to oneof the carrier services 702 and 708 that are specified by pointers 714and actually carrying the contents of the broadcasting service.

FIG. 8 illustrates a determination of edge cells for various carrierservices within an MBSFN, according to an exemplary embodiment. Forexample, an MBSFN 802 includes carrier services 1, 2, 3, and 5. Aplurality of cells (804-812) are illustrated showing the carrierservices provided within each of the cells from carrier services 1, 2,3, and 5. For example, in cell 804, the MBMS or broadcasting servicesare provided by carrier services 2, 3, and 5. Cell 804 additionally canbe considered an edge cell with respect to carrier service 3, sincecells 805, 809, 810, and 811 do not provide carrier service 3. Cell 804can also be considered an edge cell for carrier service 5, since cells805, 806 and 807 do not provide carrier service 5. An LCM value based onservice identity numbers can be calculated to determine edge cells withrespect to carrier services. For example, for cell 804, the LCM valuefor service identities for the carrier services 3 and 5, for which cell804 serves as an edge cell, is 15. Accordingly, that value may be storedwith respect to cell 804. Then, the UE can determine by checking the LCMfunction whether it is located within an edge cell of carrier 3 or 5service. Accordingly, if it is in such an edge cell, the UE can read thepointers described with respect to FIG. 7 to seek carrier services thatprovide broadcasting services in another cell of MBSFN 802.

In the exemplary embodiment illustrated in FIG. 8, these pointerspointing to locations of carrier services may be stored in SIBs orMCCHs.

FIG. 9 illustrates a block diagram of a base station 900, according toan exemplary embodiment. For example, the base station 900 may be anybase station noted above, as explained in the embodiments shown in FIGS.1-8. Referring to FIG. 9, base station 900 may include one or more ofthe following components: at least one central processing unit (CPU) 902configured to execute computer program instructions to perform variousprocesses and methods; random access memory (RAM) 904 and read onlymemory (ROM) 906 configured to access and store information and computerprogram instructions; storage 908 to store data and information;database 910 to store tables, lists, or other data structures; I/Odevices 912; interfaces 914; antennas 916, etc. Each of these componentsis well known in the art and will not be discussed further.

FIG. 10 illustrates a block diagram of a UE 1000, according to anexemplary embodiment. For example, UE 1000 may be any UE noted above, asexplained in the embodiments shown in FIGS. 1-8. Referring to FIG. 10,UE 1000 may include one or more of the following components: one or morecentral processing units (CPU) 1002 configured to execute computerprogram instructions to perform various processes and methods; randomaccess memory (RAM) 1004 and read only memory (ROM) 1006 configured toaccess and store information and computer program instructions; storage1008 to store data and information; database 1010 to store tables,lists, or other data structures; I/O devices 1012; interfaces 1014;antennas 1016, etc. Each of these components is well known in the artand will not be discussed further.

While certain features and embodiments have been described, otherembodiments will be apparent to those skilled in the art fromconsideration of the specification and practice of the embodimentsdisclosed herein. Furthermore, although aspects of embodiments have beendescribed in part as software, computer-executable instructions, and/orother data stored in memory and other storage media, one skilled in theart will appreciate that these aspects can also be stored on or readfrom other types of tangible, non-transitory computer-readable media,such as secondary storage devices like hard disks, floppy disks, orCD-ROMs, or other forms of RAM or ROM. Further, the steps of thedisclosed methods may be modified in various ways, including byreordering steps and/or inserting or deleting steps, without departingfrom the principles of the invention.

It is intended that the specification and examples be considered asexemplary only, with a true scope and spirit of the invention beingindicated by the following claims.

1. A method of providing service among a plurality of MulticastBroadcast Single Frequency Networks (MBSFNs), wherein each MBSFNcontains one or more cells, while a user equipment (UE) of a wirelesscommunication system receives a broadcasting service in a serving cellof the one or more cells in one of the MBSFNs, the method comprising:storing a pointer in data to be transmitted by a base stationcorresponding to the serving cell in a first one of the MBSFNs, thepointer stored in a multimedia broadcast multicast service (MBMS)control channel (MCCH) of the first MBSFN and pointing to either alocation of MCCH or MBMS data in a second one of the MBSFNs, or thepointer stored in a system information block of the first MBSFN andpointing to the location of the MCCH in the second MBSFN or the locationof the MCCH in the first and the second MBSBNs; and transmitting thedata by the base station for the first MBSFN for receipt by the UE. 2.The method of claim 1, wherein storing the pointer in data comprisesstoring the pointer in data corresponding to edge cells of the one ormore cells in the first MBSFN.
 3. The method of claim 1, furthercomprising sharing the serving cell by the first MBSFN and the secondMBSFN.
 4. The method of claim 1, wherein the system information block ofthe first MBSFN contains frequency information of the first MBSFN, thesecond MBSFN, or the first MBSFN and the second MBSFN
 5. The method ofclaim 1, wherein when the pointer is stored in the MCCH of the firstMBSFN and points to the location of MBMS data in the second MBSFN, thepointer indicates that reading the MCCH of the second MBSFN could beskipped.
 6. A method of providing service among a plurality of MulticastBroadcast Single Frequency Networks (MBSFNs) for a user equipment (UE)of a wireless communication system, the method comprising: receivingdata by the UE from a base station that is included in a first one ofthe MBSFNs; determining by the UE whether the received data includes apointer to a second one of the MBSFNs, the pointer stored in amultimedia broadcast multicast service (MBMS) control channel (MCCH) ofthe first one of the MBSFNs and pointing to either a location of MCCH orMBMS data in the second one of the MBSFNs or the pointer stored in asystem information block of the first one of the MBSFNs and pointing tothe location of the MCCH in the second one of the MBSFNs or the locationof the MCCH in the first one and the second one of the MBSBNs; andsending by the UE a service join request to the second one of the MBSFNsfor continuing a MBMS being received from the first one of the MBSFNsbased on the pointer.
 7. The method of claim 6, further comprising:determining whether a serving cell is an edge cell of the first MBSFNbefore determining whether the received data includes the pointer. 8.The method of claim 7, wherein determining whether the serving cell isan edge cell comprises inspecting a list of edge cells accessible to theUE to check whether the serving cell is listed as an edge cell orperforming a calculation based on a least common multiple of edge cellidentities.
 9. The method of claim 7, if the serving cell is not an edgecell of the first MBSFN, the UE does not process the step of determiningwhether the received data includes the pointer.
 10. The method of claim7, if the serving cell is not an edge cell of the first MBSFN, the UEdoes not process the step of sending the service join request to thesecond one of the MBSFNs.
 11. The method of claim 6, wherein the systeminformation block of the first MBSFN contains frequency information ofthe first MBSFN, the second MBSFN, or the first MBSFN and the secondMBSFN.
 12. The method of claim 7, further comprising: responsive to adetermination that the pointer is stored in the MCCH of the first MBSFNand pointing to the location of MBMS data in the second MBSFN, need notreading the MCCH of the second MBSFN.
 13. A user equipment (UE) toreceive a multimedia broadcast multicast service (MBMS), comprising oneor more processors, the one or more processors being configured to:receive data from a base station that is included in a first one ofMulticast Broadcast Single Frequency Networks (MBSFNs); determinewhether the received data includes a pointer to a second one of theMBSFNs, the pointer stored in a multimedia broadcast multicast service(MBMS) control channel (MCCH) of the first one of the MBSFNs andpointing to either a location of MCCH or MBMS data in the second one ofthe MBSFNs or the pointer stored in a system information block of thefirst one of the MBSFNs and pointing to the location of the MCCH in thesecond one of the MBSFNs or the location of the MCCH in the first oneand the second one of MBSFNs; and send a service join request to thesecond one of the MBSFNs for continuing the MBMS being received from thefirst one of the MBSFNs based on the pointer.
 14. The user equipment ofclaim 13, wherein the one or more processors are further configured to:determine whether a serving cell is an edge cell of the first MBSFNbefore determining whether the received data includes the pointer. 15.The user equipment of claim 14, wherein it is determined whether theserving cell is an edge cell by inspecting a list of edge cellsaccessible to the UE to check whether the serving cell is listed as anedge cell or by performing a calculation based on a least commonmultiple of edge cell identities.
 16. The user equipment of claim 14, ifthe serving cell is not an edge cell of the first MBSFN, the UE does notprocess the step of determining whether the received data includes thepointer.
 17. The user equipment of claim 14, if the serving cell is notan edge cell of the first MBSFN, the UE does not process the step ofsending the service join request to the second one of the MBSFNs. 18.The user equipment of claim 13, wherein the system information block ofthe first MBSFN contains frequency information of the first MBSFN, thesecond MBSFN, or the first MBSFN and the second MBSFN.
 19. The userequipment of claim 13, wherein responsive to a determination that thepointer is stored in the MCCH of the first MBSFN and pointing to thelocation of MBMS data in the second MBSFN, the user equipment does notneed read the MCCH of the second MBSFN.
 20. A non-transitory computerreadable recording medium for storing one or more programs, capable ofimplementing the method according to any one of claims 6-10 and 12 afterthe program is loaded on a computer and is executed.